Should we be putting these inside a code formatting? They are, if anything, code, and I think it will read less weirdly if it's formatted that way? or are we hoping that some markdown renderers might actually try to render the latex?

@michaelpj Makes sense. I can update the patch to use code formatting instead if that’s preferred.

Edit:
Quick question, if we don’t go with $...$ or $$...$$ for math formatting, should we use plain backticks (`...`) for DocMathInline, or would it make sense to use fenced code with a latex language tag even for inline math content?

The idea behind using a latex tag or math-style blocks is to make it clearer that it’s LaTeX content. I know fenced blocks are unconventional for inline content, but I wanted to ask before finalizing.

Either way, this change is something I will really appreciate since it means I won’t have to open the documentation in a browser to see important details such as time complexity, all the important information will be in my text editor.

I think it probably makes sense to use inline-code-formatting (single backticks) for inline math, and a fenced code block (triple backticks) for display math? so that would mean we could only include the language tag for display math, but that's a downside that all users of markdown face I guess.

I updated the patch to use single backticks for inline math and fenced code blocks with the latex tag for display math, as discussed.